Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1146

reference
673-tree-1
name
1146
tree-preservation-order

undefined

673-tpo-1
uprn
address-text
point
POINT (-1.013493 50.881754)
geometry
MULTIPOLYGON (((-1.013436 50.881748,-1.013439 50.881759,-1.013447 50.881770,-1.013459 50.881778,-1.013475 50.881783,-1.013493 50.881785,-1.013510 50.881783,-1.013526 50.881778,-1.013539 50.881770,-1.013547 50.881760,-1.013550 50.881749,-1.013548 50.881738,-1.013540 50.881728,-1.013527 50.881720,-1.013512 50.881715,-1.013494 50.881713,-1.013476 50.881714,-1.013460 50.881719,-1.013448 50.881727,-1.013439 50.881737,-1.013436 50.881748)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL